Oracle Utilities Customer Care and Billing Configuration AP Request Integration Point Configure the AP Business Unit Characteristic Type For each CIS Division used, in Oracle Utilities Customer Care and Billing, the AP Business Unit to be used in Oracle JD Edwards EnterpriseOne Financial Management must be configured. Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the AP Business Unit corresponding to the CIS Division as follows. 1. Create a Characteristic TypeAdmin Menu > C > Characteristic TypeThe value for this characteristic type stores the value of the Oracle JD Edwards EnterpriseOne Financial Management AP Business Unit. In this example it is JDEBU. You will use the name of the Business Unit you have established for this purpose in Oracle JD Edwards EnterpriseOne Financial Management. 2. Set up the details on the Characteristic Type as follows: Field Label Value Comment Characteristic Type JDEBU The code associated with your characteristic type. This will be used in future steps. Description Oracle JD Edwards EnterpriseOne Financial Management Business Unit A description of the use for this characteristic type. Type of Char Value Predefined Value No freeform text is allowed, only a predefined set of values. Allow Search by Char Val Allowed Allow Searches Characteristic Value US1 The name of the Oracle JD Edwards EnterpriseOne Financial Management AP Business Unit to be used. Description US1 Business Unit 3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the CIS Division: Field Label Value Comment Characteristic Entity Distribution Code This characteristic type can be inserted on a distribution code. Configure the Company Characteristic Type For each CIS Division used, in Oracle Utilities Customer Care and Billing, the Company to be used in Oracle JD Edwards EnterpriseOne Financial Management must be configured. Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the Company corresponding to the CIS Division as follows. 1. Create a Characteristic TypeAdmin Menu > C > Characteristic TypeThe value for this characteristic type stores the value of the Oracle JD Edwards EnterpriseOne Financial Management AP Business Unit. In this example it is JDECO. You will use the name of the Company you have established for this purpose in Oracle JD Edwards EnterpriseOne Financial Management. 2. Set up the details on the Characteristic Type as follows: Field Label Value Comment Characteristic Type JDECO The code associated with your characteristic type. This will be used in future steps. Description Oracle JD Edwards EnterpriseOne Financial Management Company Code A description of the use for this characteristic type. Type of Char Val Predefined Value No freeform text is allowed, only a predefined set of values. Allow Search by Char Val Allowed Allow Searches Characteristic Value 45013 The name of the Oracle JD Edwards EnterpriseOne Financial Management Company Code to be used. Description 45013 Company Code 3. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the CIS Division: Field Label Value Comments Characteristic Entity CIS Division This characteristic type can be inserted on a CIS Division. 4. Attach the Characteristic Types, created above, to any CIS Divisions that will be used for AP Request Adjustments. In sample data an example is provided as the CA CIS Division.Admin Menu > C > CIS Division Field Label Value Comments CIS Division Example: CA The CIS Division to be used. Description Example: California A description of how the CIS Division is used. Characteristic Tab Effective Date Example: 01-01-1900 The date you wish the characteristic type and value to become active and used by the system, and therefore, the integration software. Characteristic Type Oracle JD Edwards EnterpriseOne Financial Management Business Unit The characteristic type you created above. Characteristic Value Example: US1 The value you gave to the characteristic type created above. Characteristic Type Oracle JD Edwards EnterpriseOne Financial Management Company Code The characteristic type you created above. Characteristic Value Example: 45013 The value you gave to the characteristic type created above. Note: Only fields relevant to the integration are included in this table. Configure the Offset Account Template (AAI) Characteristic Type For each Distribution Code, used for AP requests in Oracle Utilities Customer Care and Billing, the corresponding Offset Account Template be used in Oracle JD Edwards EnterpriseOne Financial Management must be configured. The account corresponding to this template will be used as a credit account for the vouchers that are created in JD Edwards by the AP Request interface. Complete the following configuration in Oracle Utilities Customer Care and Billing to reference the Offset Account Template corresponding to the Distribution Code as follows. Create a Characteristic Type Admin Menu > C > Characteristic TypeThe value for this characteristic type stores the value of the Oracle JD Edwards EnterpriseOne Financial Management Offset Account Template. In the example below, the AAI name created in JD Edwards is PCREFD and the Characteristic value to be specified for the distribution codes corresponding to AP Requests is REFD. 5. Set up the details on the Characteristic Type as follows: Field Label Value Comments Characteristic Type TEMPLATE The code associated with your characteristic type. This will be used in future steps. Description Oracle JD Edwards EnterpriseOne Financial Management Offset Account Template A description of the use for this characteristic type. Type of Char Value Predefined Value No freeform text is allowed, only a predefined set of values. Allow Search by Char Val Allowed Allow Searches Characteristic Value REFD The name of the Oracle JD Edwards EnterpriseOne Financial Management Offset Account Template to be used. Description PCREFD AAI 6. Select the Characteristic Entities tab to allow the Characteristic Type to be associated with the Distribution Code: Field Label Value Comments Characteristic Entity Distribution Code This characteristic type can be inserted on a CIS Division. 7. Attach the Characteristic Type, created above, to any distribution codes that will be used for AP Request Adjustments. In sample data an example is provided as the A/P - OVPY Distribution Code that is attached to the REFUNDAP Adjustment Code.Admin Menu > D > Distribution Code Field Label Value Comments Distribution Code Example: A/P-OVPY The distribution code to be used for financial transactions of a certain type. Description Example: AP overpayment refund A description of how the distribution code is used. GL Account Algorithm GLCSNT-DFLT The standard product or customer modified algorithm you use for determining the GL Account String from the distribution code. GL Account Details 1 of 1 Create at least one set of account details as needed by your chosen algorithm above. Only one will be used based on status and effective date. Effective Date 01-01-1900 The date you wish the following GL Account string to become active and used by the system, and therefore, the integration software. Status Active Only active status accounts will be used by the product and therefore, the integration. GL Account US1.10000.111 Input the GL Account String as explained above. Characteristic Type Oracle JD Edwards EnterpriseOne Financial Management Offset Account Template The characteristic type you created above. Characteristic Value Example: REFD The value you gave to the characteristic type created above. AP Data Integration Point No Oracle Utilities Customer Care and Billing configuration is required to enable this integration point. AP payment data is extracted from Oracle JD Edwards EnterpriseOne Financial Management when an AP Request invoice is paid. This data is then translated by the BPEL service and inserted into the Oracle Utilities Customer Care and Billing AP Request that initiated the invoice in the first place. Oracle BPEL Process Manager invokes the Oracle Utilities Customer Care and Billing service, named C1AdjustmentMaintenance, when a payment is canceled and the liability is closed in Oracle JD Edwards EnterpriseOne Financial Management. The service will use the cancel reason contained in its configuration when canceling the adjustment associated with an AP Request. The sample data cancel reason comes pre-configured as "APVC' (Accounts Payable Void Check) in Oracle Utilities Customer Care and Billing version 2.2 and later. You should verify that the cancel service C1AdjustmentMaintenance is configured and that the Cancel Reason to which it refers is also configured correctly. Admin Menu > X > XAI Inbound Service Field Label Value Comments XAI in Service Name AdjustmentMaintenance This service is used to change data associated with adjustment transactions. Description AdjustmentMaintenance for AP Cancel Long Description AdjustmentMaintenance for AP Cancel Active Checked Active check box checked Request Schema C1AdjustmentMaintenance.xsd Used by BPEL to call this service. Response Schema C1AdjustmentMaintenance.xsd Used by BPEL to receive the response from this service. Transaction Type Update Service used to update an existing adjustment transaction. You may wish to test this service using XAI Dynamic Submission as follows: Admin Menu > X > XAI Dynamic Submission Field Label Value Comment XAI in Service Name AdjustmentMaintenance This service is used to change data associated with adjustment transactions. Transaction Type Update Cancel Checked Cancel check box checked. Adjustment ID Example: 078644601179 The key value of the adjustment for which you wish to test the cancel service. Cancel Reason Example: APVC AP Void Check Cancel reason. This must be a configured cancel reason. Click the submit button and review the results.